Radiocommunication module executing a main software and a client software comprising several client applications

ABSTRACT

The invention concerns a radiocommunication module, of the type hosting and executing a main software providing in particular radiocommunication functions and comprising means for executing drive controls, sent to it by at least a driver client software. The invention is characterised in that the radiocommunication module further hosts and executes at least a client software comprising a main client application and at least a secondary (slave) client application. The processing operations carried out by the onboard client software are distributed between the main and secondary client applications. The onboard client application acts: as a driver client software, sending drive controls to the main software, and receiving from it responses, resulting from the execution of some of the drive controls; and/or as a supervising client software, managing the execution of the drive controls sent by an (external) driver client software hosted and executed by a third party equipment co-operating with the radiocommunication module.

[0001] The domain of this invention is radiocommunication systems, and particularly but not exclusively the GSM (Global System for Mobile Communications) standard, DCS 1800 (Digital Cellular System 1800 MHz), PCS 1900 (Personal Communication system), GPRS (General Packet Radio Service) or UMTS (Universal Mobile Telecommunication System).

[0002] More precisely, the invention relates to a radiocommunication module. Remember that the radiocommunication module is an essential element of a radiotelephone. It hosts and executes a main software (commonly called “radiocommunication software” or “GSM software”) that in particular performs wireless communication functions (radiocommunication) and controls various other hardware elements (screen, keyboard, loudspeaker, etc.) of the radiotelephone.

[0003] Normally (first application), the radiocommunication module is included in a terminal (or ME for “Mobile Equipment”) that cooperates with a SIM (Subscriber Identity Module) card.

[0004] Other applications are now envisaged for the above mentioned radiocommunication module.

[0005] In particular, it has been proposed to integrate the radiocommunication module in devices other than radiocommunication terminals but that still require a wireless communication function (second application). For example, telemetry devices (for reading meters), alarm devices or bank card readers.

[0006] It has also been proposed to supply the radiocommunication module in independent form (third application); it is then qualified as a modem. This type of modem does not contain any hardware man-machine interface element (screen, keyboard, loudspeaker, etc.). It is designed to cooperate with a terminal equipment (supporting a client software), that does have hardware man-machine interface elements. In particular, but not exclusively, the terminal equipment may be a micro-computer. In general, the terminal equipment hosts and executes a client driver software that controls the radiocommunication module, using a set of driver commands in the AT format. The AT (for ATtention command) commands enable the Terminal Equipment (TE) to request the radiocommunication terminal to which it is connected to perform some predetermined actions. To achieve this, the main software (hosted on the radiocommunication module) comprises means of executing AT commands sent to it by the client driver software (hosted on the terminal equipment).

[0007] For further information about AT commands, refer firstly to the ETSI “GSM 07.05” and “GSM 07.07” standards, and secondly to the ITU-T recommendation V25ter which are inserted herein by reference.

[0008] In general, a radiocommunication module can be driven by a terminal equipment using AT commands not only within the framework of the above mentioned third application (radiocommunication module forming a modem), but also within the context of the first and second applications mentioned above (radiocommunication module included in a radiocommunication terminal or other system).

[0009] In other words, regardless of what application is envisaged, the radiocommunication module may be driven by a terminal equipment with which it cooperates (usually through a serial link). In this case, a client driver software (comprising a “client external application”), hosted and executed by the terminal equipment, sends AT commands to a main software, hosted and executed by the radiocommunication module, so that the radiocommunication module can execute them.

[0010] As shown in FIG. 2, operation of the existing technique used for terminal equipment to drive a radiocommunication module may be summarized as follows:

[0011] step “1”: the client external application (client driver software) 2 sends an AT command;

[0012] step “2”: the serial link 5 transmits the AT command to the AT command execution means 4 included in the main software 3 hosted and executed by the radiocommunication module 1;

[0013] step “3”: the execution means 4 execute the AT command;

[0014] step “4”: after execution, the execution means 4 send an AT response to the client external application 2;

[0015] step “5”: this response is sent through the serial link 5;

[0016] step “6”: the client external application 2 receives the response.

[0017] Each of these steps is shown in FIG. 2 by a circle in which the number of the step concerned is entered. The same convention is adopted in the following figures related to this invention (and that are described in detail in the remainder of the description).

[0018] The existing technique for driving a radiocommunication module by terminal equipment has several disadvantages.

[0019] Firstly, it requires two sets of resources (processor and memory). The radiocommunication module comprises a processor and a memory (first set of resources) and the terminal equipment also has a processor and a memory (second set of resources). Therefore, the existing technique mentioned above is expensive in terms of equipment and energy consumption.

[0020] Another disadvantage of the above mentioned existing technique is that the radiocommunication module is entirely driven by the terminal equipment. The client driver software hosted on and executed by the terminal equipment is the “master”, while the main software hosted and executed by the radiocommunication module, is the “slave”.

[0021] In order to overcome these disadvantages with the state of the art, the applicant (Wavecom Company) deposited a French patent application No. FR 0103909 on Mar. 22, 2001 entitled “Radiocommunication module hosting and executing a client software, and corresponding process for use of a client driver software”. This application FR 0103909, the texts and the drawings of which are inserted herein by reference, proposes a new technique for driving a radiocommunication module consisting of hosting at least one client software on the radiocommunication module to act as a client driver software and/or to act as a client supervision software.

[0022] Thus, if the client embedded software acts as a client driver software, the radiocommunication module operates independently and inexpensively. In this case, the radiocommunication module does not need to cooperate with a terminal equipment, and the main software and the client driver software use the same resources (same processor and same memory).

[0023] Furthermore, if the client embedded software acts as the client supervision software, the radiocommunication module is not restricted to acting as a slave with respect to the terminal equipment that executes the client driver software. The client supervision software is executed by the radiocommunication module, and manages the driving requested by the client driver software and executed by the terminal equipment. In this case, it will be noted that the client embedded software is software that is additional to the state of the art configuration mentioned above. However, this additional software is inexpensive because it uses the same resources (processor and memory) as the main software also hosted by the radiocommunication module.

[0024] In one preferred embodiment of the new technique mentioned above:

[0025] the main software comprises particularly a binary file containing the main application;

[0026] the client software comprises particularly a first binary file containing the client application, and a second binary file (for example in the form of a previously compiled library) containing an interface application between source functions associated with the client application, and execution functions associated with the main application.

[0027] This new technique for driving a radiocommunication module may be seen as a software platform, to enable clients to develop their own client applications and to download them in radiocommunication modules.

[0028] In the preferred embodiment mentioned above, the main software and the interface application are “proprietary” binary files developed by the radiocommunication module manufacturer, while the client application is a “client” binary file developed by the client.

[0029] Remember that the process for development of a binary file comprises the following steps:

[0030] write source files, for example in the “C” language;

[0031] compile these source files, so as to generate object files (in machine language for the microprocessor located on the radiocommunication module);

[0032] link edit the object files (compiled source files) so as to generate a binary file (that is then downloaded in the radiocommunication module).

[0033] In the context of the above-mentioned new technique for driving a radiocommunication module, the purpose of this invention is to facilitate the task of the client in the development process of a client application.

[0034] Another purpose of the invention is to propose a simple and efficient solution to dialogue problems between applications (main and secondary client) that result from use of the general concept of this invention.

[0035] We will now briefly mention two known techniques of solving dialogue problems between two applications, with the disadvantages of each.

[0036] According to a first known technique, dialogue problems between two software applications are solved during link editing. But this makes it necessary to know all dialogue points. Furthermore, exchanging all dialogue source functions between two applications makes it necessary for each application to adapt to the other. The result is that the developer of one application (secondary application) must write a different version of this application for each client that wants to integrated it into his applications (main applications).

[0037] A second known technique of solving dialogue problems between two applications consists of using mechanisms such as dynamic link editing. With this type of mechanism, only the functions actually used have to be loaded into memory. For example, this technique may be DLL (Dynamic Link Library) used in Windows (registered trademark). Unfortunately, this technique requires large amounts of memory and is unsuitable for use when there are severe constraints in terms of CPU, memory and real time in radiocommunication modules.

[0038] These various objectives, and others that will become clear later, are achieved according to the invention using a radiocommunication module of the type hosting and executing a main software that in particular performs radiocommunication functions, the said main software comprising means of executing driver commands sent to the main software by at least one client driver software and belonging to a predetermined set of driver commands. According to the invention, the said radiocommunication module also hosts and executes at least one client software, called the client embedded software, comprising a client main application and at least one client secondary application, slave of the client main application, the processing done by the said client embedded software being distributed between the said client main application and the said at least one client secondary application. The client embedded software and the main software comprise means of enabling the client embedded software to perform at least one of the following two roles:

[0039] the role of a client driver software sending driver commands to the main software, and receiving responses from the main software resulting from the execution of some of the driver commands,

[0040] the role of a client supervision software, managing execution of driver commands sent by a client driver software, called the client external software, hosted on and executed by terminal equipment cooperating with the radiocommunication module.

[0041] Therefore, this invention is in the context of the above mentioned new technique for control of radiocommunication module, according to which the radiocommunication module hosts and executes a client software that can act as a client driver software and/or a client supervision software.

[0042] In this context, the general aim of the invention consists of using a client “multiblock” application comprising a client main application combined with one or several client secondary application(s), rather than a client “monoblock” application. Each client secondary application is a slave application of the client main application that calls it, in terms of starting and stopping. But once it has been started, the client secondary application can access all execution functions made available by the main software (through a subscription mechanism to a service for sending messages from the main software that will be described later), completely independently of the client main application.

[0043] Client secondary applications are “elementary blocks” that may be supplied to clients by a third party developer (typically the manufacturer of the radiocommunication module). Thus, the development work done by the client is reduced because all he develops is the “client main application” that subcontracts some processing by calling one or more client secondary applications.

[0044] Note that the client can also develop client secondary applications himself, if he would like to call them in the different client main applications that he is developing.

[0045] In a first preferred embodiment of the invention, the said client software comprises a binary file containing the said client main application and the said at least one client secondary application.

[0046] In this case, the client secondary application is preferably supplied in the form of an object file. Thus, the source file is not provided, in order to protect the proprietary (or third party) know how. The object file containing the client secondary application must be link edited with the object file(s) containing the client main application, and the binary file resulting from this link editing is downloaded into the module.

[0047] In a second preferred embodiment of the invention, the said client software comprises a first binary file containing the said client main application, and at least one second binary file, each containing at least one client secondary application.

[0048] In this case, the client secondary application is supplied in the form of a binary file. Thus, as in the other case, the source file is not communicated in order to protect proprietary (or “third party”) know how. The binary file containing the client secondary application may be downloaded directly into the module.

[0049] Preferably, the following features are provided to enable the client embedded software to act as client driver software:

[0050] the client embedded software comprises means of sending driver commands to execution means included in the main software;

[0051] the main software comprises means of sending responses resulting from the execution of some driver commands by the execution means included in the main software, to the client embedded software;

[0052] the client embedded software comprises means of processing responses sent to it by the main software.

[0053] Preferably, the following features are provided to enable the client embedded software to act as client supervision software

[0054] the main software comprises means of preparsing commands as a function of a determined preparsing policy, so as to transmit driver commands from the client external software to the client embedded software and/or to execution means contained in the main software;

[0055] the client embedded software includes means of processing driver commands switched to it by the said preparsing means.

[0056] In this way, the client embedded software can:

[0057] either do nothing, the commands being sent only to the main software, which executes them directly;

[0058] or filter commands transmitted to it without being executed by the main software. For example, the client embedded software may thus decide which commands should be executed by the main software and the commands for which a response should be made without execution, as a function of determined criteria;

[0059] or “spy” commands that it receives a copy of, and which are also executed directly by the main software.

[0060] Advantageously, the client embedded software comprises means of selecting the preparsing policy applied by the said preparsing means, among a set of preparsing policies such as:

[0061] driver commands originating from the client external software are sent only to execution means within the main software;

[0062] driver commands originating from the client external software are sent only to the client embedded software;

[0063] driver commands originating from the client external software are sent to the execution means included in the main software and to the client embedded software.

[0064] Advantageously, the said command processing means take at least one decision for each command, belonging to the group including:

[0065] send the driver command to the execution means included in the main software, the client embedded software comprising means of sending driver commands to the execution means for this purpose;

[0066] supply or do not supply a response, only as a function of at least one item of information about the command, without executing the command, the client embedded software comprising means of sending the response to the client external software for this purpose through the main software.

[0067] Advantageously, to enable the client embedded software to act as client supervision software:

[0068] the main software comprises means of preparsing responses as a function of a determined response preparsing policy, so as to transmit responses resulting from the execution of some driver commands by execution means included in the main software, to the client embedded software and/or to the client external software;

[0069] the client embedded software comprises means of processing responses switched to it by the said response preparsing means.

[0070] In this way, the client embedded software can:

[0071] either not take any action, responses generated by the main software being transmitted only to the client external software;

[0072] or filter responses transmitted to it without being transmitted to the client external software. For example, the client embedded software can thus decide what responses should be sent to the client external software (modified or not modified) as a function of defined criteria, and what responses should not be transmitted to this client external software;

[0073] or “spy” responses of which it receives a copy and which are also sent directly to the client external software.

[0074] Advantageously, the client embedded software comprises means of selecting the response preparsing policy applied by the said response preparsing means, among a set of response preparsing policies such as the following:

[0075] responses originating from execution means are transmitted only to the client external software;

[0076] responses originating from execution means are transmitted only to the client embedded software;

[0077] responses originating from execution means are transmitted to the client embedded software and to the client external software.

[0078] Preferably, the said radiocommunication module is included within a device belonging to the following group:

[0079] radiocommunication terminals;

[0080] devices other than radiocommunication terminals necessitating a wireless communication feature;

[0081] modems.

[0082] Preferably, the said main software comprises at least one main application associated with a set of execution functions, each enabling the execution of at least one of the said driver commands. Each of the said client main and secondary applications is associated with a set of source functions, each enabling sending or receiving driver commands or responses to driver commands, to or from the main application. The main software and/or the said client embedded software comprise an application interface used to interface the said source functions with the said execution functions.

[0083] The result is to limit development costs, due to the fact that the interface application (also called the application interface library in the following) can be used with different client applications (main applications), or even with different main software, once it has been developed.

[0084] In one advantageous embodiment of the invention, the set of source functions associated with the client main application in particular comprises a client main application initialisation source function that is called when the radiocommunication module is started.

[0085] Preferably, the set of source functions associated with the client main application comprises a source function for subscription to a service for sending messages originating from the main software. At the time of this subscription, the client main application sends the address of a message processing source function in which the client main application would like to receive messages from the main software, to the main software.

[0086] This subscription mechanism to a service for sending messages originating from the main software enables the client main application to call all execution functions provided by the main software, while being able to receive messages sent by the main software for execution of these functions.

[0087] Preferably, the set of source functions associated with the client secondary application comprises in particular a source function for initialisation of the client secondary application that is called by the client main application.

[0088] Preferably, the set of source functions associated with the client secondary application comprises a source function for subscription to a service for sending messages originating from the main software. At the time of this subscription, the client secondary application sends the address of a source message processing function to the main software, in which the client secondary application would like to receive messages originating from the main software.

[0089] Advantageously, the said source initialisation function of the client secondary application comprises at least one parameter enabling the use of a dialogue mechanism between the client main application and the client secondary application.

[0090] Preferably, the set of source functions associated with the client secondary application also comprises a source function for stopping the client secondary application called by the client main application.

[0091] Preferably, the set of source functions associated with the client secondary application comprises a source function for unsubscription from the said service for sending messages originating from the main software.

[0092] In this manner, the client main application only needs to know this dialogue point (source function for initialisation of the client secondary application) and its corresponding function described below (source function for stopping the client secondary application). Therefore, it is a simple and efficient solution to dialogue problems between a client main application and a client secondary application. The developer of a client secondary application does not need to write one version for each client that wants to integrate it into its client main applications. All he needs to do is to inform him about the two dialogue points mentioned above.

[0093] Note that it is important to avoid two developers of client secondary applications from using identical dialogue points. For example, this can be achieved if each developer asks a central service for a unique identifier for each client secondary application that he would like to develop.

[0094] Furthermore, the dialogue mechanism between the client main application and the client secondary application enables the client secondary application to notify the client main application about the execution results of its task(s). The dialogue may be two directional or single-directional.

[0095] Advantageously, the said message type belongs to the group comprising:

[0096] message containing a response to a driver command previously sent to the main software by the client embedded software;

[0097] message containing an unsolicited driver command;

[0098] message containing a driver command sent by a client external software through the main software;

[0099] message containing a response resulting from execution of a driver command sent by the client external software, by the main software;

[0100] message sent on expiration of a timeout.

[0101] In one preferred embodiment of the invention, the said set of driver commands is a set of standard AT commands. This enables fast development of the client embedded software, since AT commands are well known and are already used for the development of client external software (hosted on the terminal equipment). This also facilitates development of a client software strongly based on an existing client external software.

[0102] The invention also relates to a process for implementation of a client software for the control of a radio communication module, the said radiocommunication module being of the type that hosts and executes a main software particularly performing radiocommunication functions, the said main software comprising means of executing driver commands sent to the main software by the said client driver software and belonging to a predetermined set of driver commands. According to the invention, the said radiocommunication module hosts and also executes at least one client software, called the client embedded software, comprising a client main application and at least one client secondary application, slave of the client main application, the processing done by the said client embedded software being distributed between the said client main application and the said at least one client secondary application. The client embedded software and the main software dialogue with each other such that the client embedded software performs at least one of the following two roles:

[0103] the role of the said client driver software to send driver commands to the main software, and to receive responses following execution of some of the driver commands from the main software;

[0104] the role of a client supervision software, managing execution of driver commands sent by the said client driver software, the said client driver software called the client external software being hosted on and executed by terminal equipment cooperating with the radiocommunication module.

[0105] Other characteristics and advantages of the invention will become clear after reading the following description of a preferred embodiment of the invention given as a non-limitative example, and the attached drawings, in which:

[0106]FIG. 1 shows a simplified diagram of a particular embodiment of a radiocommunication module according to this invention, showing the client main application and the client secondary application;

[0107]FIG. 2 (prior art) shows operation of the existing technique for driving a radiocommunication module by terminal equipment;

[0108]FIG. 3 shows a mechanism for starting the client main application and subscription of this application to a service for sending messages originating from the main software;

[0109]FIG. 4 shows a mechanism for starting the client secondary application and subscription of this application to a service for sending messages originating from the main software;

[0110]FIG. 5 shows a mechanism for stopping a client secondary application and for unsubscribing this application from the service for sending messages originating from the main software;

[0111]FIG. 6 shows an example of processing (sending a command and receiving the corresponding response) that could be done by the client secondary application, if the radiocommunication module operates according to a first embodiment of the invention in which the client embedded software acts as a client driving software.

[0112] Therefore, the invention relates to a radiocommunication module hosting and executing a main software and at least one client embedded software, using the same set of resources (processor and memory).

[0113] Conventionally, in particular the main software (for example a “GSM software”) performs radiocommunication functions and comprises means of executing driver commands (sent to it by a client driver software).

[0114] The client embedded software (concept specific to this invention) can act as:

[0115] a client driver software, and/or

[0116] a client supervision software.

[0117] In the remainder of this description, it is assumed that the driver commands are AT commands. However, it is clear that this invention is not restricted to this type of driver command.

[0118] In the particular embodiment shown in FIG. 1, the main software 3 comprises a main application 3 a based particularly on a set of execution functions, each enabling the execution of at least one AT command.

[0119] Furthermore, the client embedded software 6 comprises:

[0120] a client main application 6 a, associated with a set of source functions, each enabling sending AT commands to a main application 3 a, or receiving AT commands from this application;

[0121] a client secondary application 6 c, also associated with a set of source functions like those mentioned above;

[0122] an interface application 6 b, enabling interfacing of source functions (from the client main application 6 a and the client secondary application 6 c) with execution functions (of the main application 3 a).

[0123] Thus, the client main application 6 a communicates with the main application 3 a through the interface application 6 b. Similarly, the client secondary application 6 c communicates with the main application 3 a through the interface application 6 b.

[0124] Consequently, each application (main 6 a, secondary 6 c and interface 6 b) comprises an “API” (Application Programming Interface). Note that an API is a description of communication rules corresponding to a specific functional assembly.

[0125] The client main application 6 a comprises an “Application Mandatory API” block forming an interface describing functions that will have to be defined in the client main application.

[0126] The client secondary application 6 c also comprises an “Application Mandatory API” block (partially identical to the block with the same name included in the client main application) forming an interface describing functions to be defined in the client secondary application.

[0127] The interface application (or the application interface library) 6 b, comprises the three following blocks:

[0128] an “AT command API” block forming an interface describing access to ATI commands, this interface describes functions located in the application interface library;

[0129] an “OS API” block forming an interface describing access to operating system functions, this interface describes functions located in the application interface library;

[0130] a “Standard API” block forming an interface describing the access to standard functions, this interface describes functions located in the application interface library.

[0131] In the main software 3, the main application 3 a comprises:

[0132] an “AT command API” block, similar to the block with the same name included in the interface application 6 b;

[0133] an “OS API” block, similar to the block with the same name included in the interface application 6 b.

[0134] The main application 3 a forms the core of the main software 3, and the client main application 6 a, the client secondary application 6 c, and the interface application 6 b form the kernel of the client embedded software 6.

[0135] For example, the interface application 6 b may be a binary file in the form of a previously compiled library.

[0136] The client main application 6 a is a binary file resulting from link editing between a plurality of object files (themselves resulting from compilation of source files).

[0137] The following two variants may be considered for the client secondary application 6 c:

[0138] either it is supplied in the form of an object file and in this case the object file is taken into account at the time of link editing to generate the binary file containing the client main application 6 a. In other words, a particular binary file contains the client main application and the client secondary application;

[0139] or it is supplied directly in the form of a binary file. In other words, the client main application 6 a and the client secondary application 6 c are contained in two distinct binary files.

[0140] The client embedded software 6 and the main software 3 each use a distinct part of the same RAM. The client defines the size of the memory stack necessary for correct execution of the client embedded software. An attempt by one of the two software programs to access part of the RAM reserved for the other software will stop operation.

[0141] We will now present a mechanism for starting the client main application 6 a and subscription of this application to a service sending messages originating from the main software 3, with reference to FIG. 3.

[0142] Elements conventionally included in a radiocommunication module and described above with reference to FIG. 2 (prior art) have the same numeric references. Thus, the radiocommunication module 1 hosts and executes a main software 3 in particular comprising means of executing AT commands.

[0143] Furthermore, according to the invention and as presented above with reference to FIG. 1, the radiocommunication module 1 hosts and also executes a client embedded software 6 that acts as client driving software or client supervision software, and in particular comprises a client main application 6 a, a client secondary application 6 c and an interface application 6 b.

[0144] Operation of this mechanism to start the client main application and to subscribe it to a service for sending messages may be summarized as follows:

[0145] step “1”: the main software 3 detects the presence of a client main application 6 a and starts it;

[0146] step “2”: the client main application 6 a is started through the interface application 6 b, which calls a source function for initialization of the client main application 6 a, within the client main application 6 a. This source function (“wm_apmAppliInit”) is presented in detail in the remainder of the description;

[0147] step “3”: within the client main application 6 a, the “wm_apmAppliInit” source function initialises the client main application. As explained in detail in the following steps (“14” to “6”), this initialisation consists particularly of providing the main software 3 with the address of a source function (for example “wm_apmAppliParser”) so that the client main application 6 a can receive messages originating from the main software;

[0148] step “4”: the client main application 6 a calls a source function for subscription to a service for sending messages originating from the main software (“wm_osMsgParserSubscribe”). This source function is described in detail in the remainder of the description;

[0149] step “5”: the interface application 6 b calls the appropriate execution function(s) for registering the subscription to the service for sending messages to the client main application 6 a, within the main software 3;

[0150] step “6”: the main software 3 produces the registration requested by the client main application 6 a through the interface application 6 b.

[0151] According to one variant, the client main application 6 a calls the “wm_osMsgParserSubscribe” source function whenever it wishes (independently of the execution of the source initialisation function of the client main application 6 a).

[0152] We will now present a mechanism for starting the client secondary application 6 c and for subscribing it to a service for sending messages from the main software 3, with reference to FIG. 4.

[0153] Operation of this mechanism can be summarized as follows:

[0154] step “1”: after receiving a message in its-source function “wm_apmAppliParser( )”, the client main application 6 a calls a source function of the client secondary application 6 c, namely the source function to initialise the client secondary application 6 c (“wm_app2Pipe(init)”). This source function (which must be known to the client main application 6 a) is described in detail in the remainder of the description;

[0155] step “2”: the source function “wm_app2Pipe(init)” within the client secondary application 6 c, initialises the client secondary application 6 c. As explained in detail in the following steps (“3” to “5”), this initialisation consists particularly of providing the main software 3 with the address of a source function (for example “wm_app2MsgParser”) that the client secondary application 6 c uses to receive messages originating from the main software 3;

[0156] step “3”: the client secondary application 6 c calls the source function for subscription to a service for sending messages originating from the main software (“wm_osMsgParserSubscribe”). This source function is presented in detail in the remainder of the description;

[0157] step “4”: the interface application 6 b calls the appropriate execution function(s) within the main software 3, to register the subscription to the service for sending messages addressed to the client secondary application 6 c;

[0158] step “5”: the main software 3 generates the registration requested by the client secondary application 6 c, through the interface application 6 b.

[0159] After the client secondary application 6 c has been started in this way, it performs its function (set of processing or tasks) independently of the client main application 6 a. As described in detail below, it uses the set of execution functions provided by the main software 3 for this purpose.

[0160] According to one variant, the client secondary application 6 c calls the “wm_osMsgParserSubscribe” source function whenever it wishes (independently of execution of the source function to initialise the client secondary application 6 c).

[0161] Note that the source initialisation function of the client secondary application may comprise at least one parameter for implementing a dialogue mechanism between the client main application 6 a and the client secondary application 6 c. This characteristic of the invention is described in detail in the remainder of the description.

[0162] We will now describe the mechanism for stopping the client secondary application 6 c and unsubscribing it from the service for sending messages originating from the main software 3, with reference to FIG. 5.

[0163] The operation of this mechanism may be summarised as follows:

[0164] step “1”: after receiving a message in its source function “wm_apmAppliParser( )”, the client main application 6 a calls a source function of the client secondary application 6 c, namely the source function to stop the client secondary application 6 c (“wm_app2Pipe(stop)”) This source function (which must be known to the client main application 6 a) is described in detail in the remainder of the description;

[0165] step “12”: the source function “wm_app2Pipe(stop)” within the client secondary application 6 c, carries out processing to stop the client secondary application 6 c. As explained in detail in the following steps (“3” to “5”), for the client secondary application 6 c this processing consists particularly of unsubscribing from the service to send messages originating from the main software 3;

[0166] step “3”: the client secondary application 6 c calls the source function for unsubscribing from the service for sending messages originating from the main software (“wm_osMsgParserUnsubscribe”). This source function is presented in detail in the remainder of the description;

[0167] step “4”: the interface application 6 b within the main software 3 calls the appropriate execution function(s), called the unsubscription function(s), from the service for sending messages addressed to the client secondary application 6 c;

[0168] step “5”: the main software 3 stops the registration requested by the client secondary application 6 c, through the interface application 6 b.

[0169] We will now describe an example of processing that can be done by the client secondary application, to release the client main application 6 a, with reference to FIG. 6.

[0170] In this example, it is assumed that:

[0171] the radiocommunication module operates according to a first embodiment of the invention, in which the client embedded software acts as the client driver software;

[0172] the processing consists of the client secondary application 6 c sending a command and receiving the corresponding response;

[0173] the client secondary application 6 c was initialised and subscribed to the service for sending messages from the main software 3 (see FIG. 4);

[0174] at the time of the subscription, the client secondary application 6 c gave “wm_app2MsgParser( )” as the message reception source function.

[0175] Operation of this processing example can be summarized as follows:

[0176] step “1”: the secondary application 6 c calls a source function to send one or several AT commands to the main software 3, so that the main software can execute them (therefore, an “AT command processing” is done). This source function (“wm_atSendCommand”) is described in detail in the remainder of the description;

[0177] step “2”: the interface application 6 a calls the appropriate execution function(s), called the AT command processing functions, within the execution means 4 included in the main software 3;

[0178] step “₃”: the execution means 4 execute the AT command(s);

[0179] step “₄”: after execution, the execution means 4 send the AT response(s) to the client secondary application 6 c (if the sending source function was configured to do this);

[0180] step “5”: this or these responses are sent to the client secondary application 6 c, through the interface application 6 a;

[0181] step “6”: the source reception and processing function “wm_app2MsgParser( )” processes the response, within the client secondary application 6 c. This source function is the function that the client secondary application 6 c named during registration for reception of messages originating from the main software 3. The message that contains the above mentioned response(s) is a parameter of this source reception and processing function.

[0182] Note that FIG. 6 described above is transposed from FIG. 3 in the French patent application No. FR 0103909 deposited by the applicant (Wavecom company) on Mar. 22, 2001. The only difference is that the client secondary application is involved in this case (instead of the client embedded application in patent application No. FR 0103909).

[0183] A second embodiment of the invention is also provided in which the client embedded software acts as the client supervision software. In this case, the client secondary application may for example perform the following processing:

[0184] use of a command preparsing mechanism, enabling the client secondary application to filter or spy commands originating from the client external software;

[0185] use of a response preparsing mechanism, enabling the client secondary application to filter or spy responses sent to a client external software.

[0186] We will not describe these examples of processing done by the client secondary application in more detail (not shown in the figures), in the case in which the radiocommunication module operates according to the second embodiment of the invention mentioned above.

[0187] However, it should be noted that an explanatory text and figures related to the implementation of the two preparsing mechanisms mentioned above (for commands and responses) by the client secondary application, can be obtained by making the following transposition:

[0188] start from FIGS. 4 to 7 in French patent application No. FR 0103909 mentioned above and the corresponding explanatory text, and,

[0189] consider that the client secondary application is involved (instead of the “client embedded application” in patent application No. FR 0103909).

[0190] Appendix 1 contains a detailed presentation of some source functions on which the client main application 6 a and the client secondary application 6 c are based.

[0191] Optionally, for the purposes of this invention, it is also possible to use at least one of the following additional AT commands in addition to standard AT commands:

[0192] command to load a client software (AT+WDWL) to enable the client external software to load a new client software, or a new part of the client software, into the radiocommunication module;

[0193] deactivate command (AT+WOPEN) enabling the client external software to deactivate the client embedded software or part of the client embedded software.

Appendix 1 Detailed Presentation of Some Source Functions on Which the Client Main Application and the Client Secondary Application are Based

[0194] A1) “wm_apmAppliInit”:

[0195] Function to initialise the client main application; this function is called when the radiocommunication module is started.

[0196] Exact Name:

[0197] Void wm_apmAppliInit (wm_apmInitType_e InitType)

[0198] Parameters:

[0199] InitType

[0200] This parameter determines what starts the initialisation, the values are:

[0201] Typedef Enum {  WM_APM_POWER_ON  WM_APM_REBOOT_FROM_EXCEPTION }  wm_apmInitType_e;

[0202] WM_APM_POWER_ON

[0203] Normal start

[0204] WM_APM_REBOOT_FROM_EXCEPTION

[0205] The module is restarted after an exception.

[0206] A2) “wm_osMsgParserSubscribe( )”:

[0207] Function to register a client application (main or secondary) with the main software to a service for reception of messages originating from the main software. The main software memorises this function and uses it whenever it has something to transmit to the client application concerned (main or secondary).

[0208] Exact Name:

[0209] Void wm_osMsgParserSubscribe (void

[0210] *SubscribeFunction)(wm_apmMsg_t*)

[0211] Parameters:

[0212] SubscribeFunction (wm_apmMsg_t*): function provided by the caller (client main or secondary application) so that the main software can send messages to it. A prototype of this function provided is described below (“wm_apmAppliParser” for the client main application, or “wm_app2MsgParser” for the client secondary application).

[0213] Return Value:

[0214] The return parameter indicates if the subscription was accepted (TRUE) or not (FALSE).

[0215] A3) “wm_osMsgParserUnsubscribe( )”:

[0216] Function to stop registration of a client application (main or secondary) with the main software to a service for reception of messages originating from the main software. The main software forgets the previously memorized function.

[0217] Exact Name:

[0218] Bool wm_osMsgparserUnsubscribe(void(*SubsFunction)(wm_apmMsg_t *))

[0219] Parameters:

[0220] SubsFunction(wm_apmMsg_t*): function provided by the caller (main or secondary client application) so that the main software can send messages to it. This function must be the same as the function given during subscription to this service, otherwise the subscription will not be stopped.

[0221] Return Value:

[0222] The return parameter indicates if the subscription was stopped (TRUE) or not (FALSE).

[0223] A4) “wm_app2Pipe(FunctionType function, . . . )”:

[0224] Prototype of the function to be provided by the client secondary application to the client main application to be able to dialogue with it. This function has variable arguments, and the number and type or arguments depend on the first “function” parameter.

[0225] Exact Name:

[0226] Void wm_app2Pipe(FunctionType function, . . . );

[0227] Parameters:

[0228] Function: requested function. This function implies the number and type of parameters as follows. Some values are reserved (for example 0 to 127), and others (for example 128 to 255) are left free for use by particular dialogues between the client main application and the client secondary application.

[0229] A4-1) Variable parameters for function=WM_APP_FUNCTION_INIT: Void wm_app2Pipe   ( FunctionType_t function, InitType_t Init, Void   (*MainAppDialogFunction) (wm_apmMsg_t*) Void   *(*SecondaryAppDialogFunction) (wm_apmMsg_t*), );

[0230] The secondary application must be initialised and must perform its processing.

[0231] InitType_t Init: the initialisation type (APM_INIT POWER On or APM_INIT REBOOT)

[0232] Void (*Main AppDialogFunction)(wm_apmMsg_t*): address of the function that the client secondary application must use to send messages to the client main application. If the client main application does not require this function, it sends a NULL value.

[0233] Void *(*SecondaryAppDialogFunction)(wm_apmMsg_t*): The client secondary application must give the address of the function that it provides to the client main application. If the client secondary application does not provide this function, it must set the value to NULL.

[0234] A4-2) Variable parameters for function=WM_APP_FUNCTION_STOP: Void wm_app2Pipe FunctionType_t function, );

[0235] The client secondary application must stop its processing, unsubscribe from all its subscriptions and release all resources used.

[0236] A5) “wm_apmAppliParser”

[0237] Prototype of the source function that the client main application must provide to receive messages originating from the main software. The message forming a parameter of this processing function (also called the “reception” function) in particular contains an AT command or a response to an AT command.

[0238] It will be noted that everything that is described below is also applicable to the source function, in which the client secondary application would like to receive messages originating from the main software. All that changes is the function name itself (for example “wm_app2MsgParser” instead of “wm_apmAppliParser”).

[0239] Exact Name:

[0240] Bool wm_apmAppliParser(wm_apmMsg_t*Message);

[0241] Parameters:

[0242] Message

[0243] The message structure is different for each type of received message: Typedef struct {  S16  MsgTyp;  /* “MsgTyp” is a received message type to determine  the associated structure of the message body */  wm_apmBody_t  Body;  /*  “Body” is a specific  message body */ } wm_apmMsg_t; Values of “MsgTyp”:

[0244] WM_AT_SEND_RSP

[0245] The message contains a response to an AT command previously sent to the main software by the client embedded software

[0246] WM_AT_UNSOLICITED

[0247] The message contains an unsolicited AT command

[0248] WM_AT_CMD_PRE_PARSER

[0249] The message contains an AT command sent by a client external software through the main software.

[0250] WM_AT_RSP_PRE_PARSER

[0251] The message contains an AT response resulting from the main software executing an AT command originating from an external application.

[0252] WM_OS_TIMER

[0253] The message is sent on expiration of a timeout

[0254] The structure of the body is: typedef union {  /* The following includes all specific structures  associated with “MsgTyp” */ message types  /* WM_AT_SEND_RSP */    wm_atResponse_t ATResponse;  /* WM_AT_UNSOLICITED  */  wm_atUnsolicited_t  ATUnsolicited;  /* WM_AT_CMD_PRE_PARSER   */  wm atCmdPreParser_t  ATCmdPreParser;  ;/* WM_AT_RSP_PRE_PARSER   */  wm_atRspPreParser_t  ATRspPreParser  /* WM_OS_TIMER   */  wm_osTimer_t   OSTimer; } wm_apmBody_t;

[0255] Substructures of the body are as follows: Body for WM_AT_SEND_RSP:  typedef struct {   wm_atSendRspType_e Type;   u16 StrLength; /* Length of strData */   char StrData[1]; /* AT response   */  } wm_atResponse_t;  typedef enum  {   WM_AT_SEND_RSP_TO_EMBEDDED,   WM_AT_SEND_RSP_TO_EXTERNAL,   WM_AT_SEND_RSP_BROADCAST  } wm_atSendRspType_e;  (see details of the “wm_atSendCommand” function for  the description of “wm_atSendRspType_e description  ”), Body for WM_AT_UNSOLICITED:  typedef struct {   wm_atUnsolicited_e Type;   u16 StrLength;   char StrData[1];  } wm_atUnsolicited_t;  typedef enum   {   WM_AT_UNSOLICITED_TO_EXTERNAL,   WM_AT_UNSOLICITED_TO_EMBEDDED,   WM_AT_UNSOLICITED_BROADCAST  } wm_atUnsolicited_e;  (see details of the “wm_atUnsolicitedSubscription”  function for the description of “wm_atUnsolicited_e  ”). Body for WM_AT_CMD_PRE_PARSER:  typedef struct   {   wm_atCmdPreSubscribe_e Type;   u16 StrLength;   char StrData[1]  } wm_atCmdPreParser_t;  typedef enum  {   WM_AT_CMD_PRE_WAVECOM_(—)   TREATMENT, /* Default value   */   WM_AT_CMD_PRE_EMBEDDED_TREATMENT,   WM_AT_CMD_PRE_BROADCAST  } wm_atCmdPreSubscribe_e;  (see details of the “wm_atRspPreParserSubscribe”  function   for   the   description   of  “wm_atCmdPreSubscribe_e”). Body for WM_AT_RSP_PRE_PARSER:  typedef struct {   wm_atRspPreSubscribe_e Type;   u16 StrLength;   char StrData[1];  } wm_atRspPreParser_t;  typedef enum {   WM_AT_RSP_PRE_WAVECOM_(—)   TREATMENT /* Default value   */   WM_AT_RSP_PRE_EMBEDDED_TREATMENT,   WM_AT_RSP_PRE_BROADCAST  } wm_atRspPreSubscribe_e;  (see details of the “wm_atRspPreParserSubscribe”  function   for   the   description   of  “wm_atRspPreSubscribe_e”). Body for WM_OS_TIMER:  typedef struct {   u8 Ident; /* Timeout identifier   */  } wm_osTimer_t;

[0256] (see details of the “wm_osStartTimer” function for a description of “Ident”).

[0257] Returned Parameters

[0258] The return parameter indicates if the message is processed (TRUE) or not (FALSE).

[0259] A6) “wm_atSendCommand”

[0260] Function for sending at least one AT command to the main software, in which a parameter indicates the destination application(s) (namely the client embedded application (main or secondary) and/or the client external application) of the response resulting from execution of this AT command.

[0261] Exact Name: Void wm_atSendCommand (u16 AtStringSize wm_atSendRspType_e Responsetype, char *AtString,);

[0262] Parameters:

[0263] AtString

[0264] This parameter may be any type of string of AT command using ASCII characters. Several strings may be sent at the same time.

[0265] AtStringSize

[0266] Size of the previous parameter: AtString.

[0267] ResponseType

[0268] Response type Typedef enum  {  WM_AT_SEND_RSP_TO_EMBEDDED, /* Default value */  WM_AT_SEND_RSP_TO_EXTERNAL,  WM_AT_SEND_RSP_BROADCAST } wm_atSendRspType_e;

[0269] WM_AT_SEND_RSP_TO_EMBEDDED

[0270] All responses are redirected to the client embedded application (main or secondary). This is the default mode.

[0271] WM_AT_SEND_RSP_TO_EXTERNAL

[0272] All responses are redirected to the client external application (PC).

[0273] WM_AT_SEND_RSP_BROADCAST

[0274] All responses are redirected (broadcast) to the client embedded application (main or secondary) and the client external application (PC).

[0275] A7) “wm_AtUnsolicitedSubscription”

[0276] Registration function with the main software to a service for reception of unsolicited AT commands, in which one parameter indicates the destination application (namely the client embedded application (main or secondary) and/or the client external application), to which each of the unsolicited AT commands must be redirected.

[0277] Exact Name:

[0278] Void wm_atUnsolicitedSubscription(wm_atUnsolicited_e Unsolicited);

[0279] Parameters:

[0280] Unsolicited

[0281] This parameter describes actions carried out when an unsolicited AT command arrives. Typedef enum  WM_AT_UNSOLICITED_TO_EXTERNAL,  /* Default value  */  WM_AT_UNSOLICITED_TO_EMBEDDED,  WM_AT_UNSOLICITED_BROADCAST, } wm_atUnsolicited_e;

[0282] WM_AT_UNSOLICITED_TO_EXTERNAL

[0283] All unsolicited commands will be redirected to the client external application (PC) (default mode).

[0284] WM_AT_UNSOLICITED_TO_EMBEDDED

[0285] All unsolicited commands will be redirected to the client embedded application (main or secondary).

[0286] WM_AT_UNSOLICITED_BROADCAST

[0287] All unsolicited commands will be redirected (broadcast) to the client external application (PC) and the client embedded application (main or secondary).

[0288] A8) “wm_atCmdPreParserSubscribe”

[0289] Registration function with the main software to an AT command preparsing service, in which a parameter indicates the destination application(s) (namely the client embedded application (main or secondary) and/or the main application) to which each AT command originating from an external application must be directed.

[0290] Exact Name:

[0291] Void wm_atCmdPreParserSubscribe (wm_atCmdPreSubscribe_e SubscribeType);

[0292] Parameters

[0293] SubscribeType

[0294] This parameter describes the action carried out when an AT command arrives Typedef enum  WM_AT_CMD_PRE_WAVECOM_(—)  TREATMENT,   /* Default value  */  WM_AT_CMD_PRE_EMBEDDED_TREATMENT,  WM_AT_CMD_PRE_BROADCAST, } wm_atCmdPreSubscribe_e;

[0295] WM_AT CMD_PRE WAVECOM_TREATMENT

[0296] The client embedded application (main or secondary) does not want to filter (or spy) commands sent by the client external application (default mode).

[0297] WM_AT_CMD_PRE_EMBEDDED_TREATMENT

[0298] The client embedded application (main or secondary) wants to filter commands sent by the client external application.

[0299] WM_AT CMD_PRE BROADCAST

[0300] The client embedded application (main or secondary) wants to spy commands sent by the client external application.

[0301] A9) “wm_atRspPreParserSubscribe”

[0302] Registration function with the main software to an AT response preparsing service, in which a parameter indicates the destination application(s) (namely the client embedded application (main or secondary) and/or the client external application) to which each AT command originating from an external application must be directed.

[0303] Exact Name:

[0304] Void wm_atRspPreParserSubscribe (wm_atRspPreSubscribe_e SubscribeType);

[0305] Parameters

[0306] SubscribeType

[0307] This parameter describes the action carried out when an AT command arrives Typedef enum  WM_AT_RSP_PRE_WAVECOM_TREATMENT, /* Default value  */  WM_AT_RSP_PRE_EMBEDDED_TREATMENT,  WM_AT_RSP_PRE_BROADCAST, } wm_atRspPreSubscribe_e;

[0308] WM_AT_RSP_PRE_WAVECOM_TREATMENT

[0309] The client embedded application(main or secondary) does not want to filter (or spy) responses sent to the client external application (default mode).

[0310] WM_AT_RSP_PRE_EMBEDDED_TREATMENT

[0311] The client embedded application (main or secondary) wants to filter responses sent to the client external application.

[0312] WM_AT_RSP_PRE_BROADCAST

[0313] The client embedded application (main or secondary) wants to spy the response sent to the client external application.

[0314] A10) “wm_atSendRspExternalApp”

[0315] Function to send at least one response to the client external software, through the main software. This function can only be used if a prior registration has been made to the response preparsing service, in particular including redirection of a copy of responses to the client embedded application (main or secondary).

[0316] Exact Name:

[0317] Void wm_atSendRspExternalApp (u16 AtStringSize, Char *AtString,);

[0318] Parameters:

[0319] AtString

[0320] May be any type of AT response string, in ASCII characters.

[0321] AtStringSize

[0322] Size of the previous parameter: AtString

[0323] A11) “DataFlowService”

[0324] Function to send and/or receive data by the client embedded application (main or secondary), through the main software, after a data communication has been set up.

[0325] A12) “wm_osStartTimer”

[0326] Function to start a timeout, a parameter of the said starting function indicating which timeout is to be started.

[0327] A13) “wm_osStopTimer”

[0328] Function to stop a timeout, a parameter of the said stop function indicating which timeout is to be stopped. 

1. Radiocommunication module of the type hosting and executing a main software that in particular performs radiocommunication functions, the said main software comprising means of executing driver commands sent to the main software by at least one client driver software and belonging to a predetermined set of driver commands, characterised in that the said radiocommunication module also hosts and executes at least one client software, called the client embedded software, comprising a client main application and at least one client secondary application, slave of the client main application, the processing done by the said client embedded software being distributed between the said client main application and the said at least one client secondary application, and in that the client embedded software and the main software comprise means of enabling the client embedded software to perform at least one of the following two roles: the role of a client driver software sending driver commands to the main software, and receiving responses from the main software resulting from the execution of some of the driver commands; the role of a client supervision software, managing execution of driver commands sent by a client driver software, called the client external software, hosted on and executed by terminal equipment cooperating with the radiocommunication module.
 2. Radiocommunication module according to claim 1, characterised in that the said client software comprises a binary file containing the said client main application and the said at least one client secondary application.
 3. Radiocommunication module according to claim 1, characterised in that the said client software comprises a first binary file containing the said client main application and at least a second binary file, each containing at least one client secondary application.
 4. Radiocommunication module as claimed in any of claims 1 to 3, characterised in that the following features are provided to enable the client embedded software to act as client driver software: the client embedded software comprises means of sending driver commands to execution means included in the main software; the main software comprises means of sending responses resulting from the execution of some driver commands by the execution means included in the main software, to the client embedded software; the client embedded software comprises means of processing responses sent to it by the main software.
 5. Radiocommunication module as claimed in any of claims 1 to 4, characterised in that the following features are provided to enable the client embedded software to act as client supervision software: the main software comprises means of preparsing commands as a function of a determined preparsing policy, so as to transmit driver commands from the client external software to the client embedded software and/or to execution means contained in the main software; the client embedded software includes means of processing driver commands switched to it by the said preparsing means.
 6. Radiocommunication module according to claim 5, characterised in that the client embedded software comprises means of selecting the preparsing policy applied by the said preparsing means, among a set of preparsing policies such as: driver commands originating from the client external software are sent only to execution means within the main software; driver commands originating from the client external software are sent only to the client embedded software; driver commands originating from the client external software are sent to the execution means included in the main software and to the client embedded software.
 7. Radiocommunication module as claimed in any of claims 5 and 6, characterised in that the said command processing means take at least one decision for each command, belonging to the group including: send the driver command to the execution means included in the main software, the client embedded software comprising means of sending driver commands to the execution means for this purpose; supply or do not supply a response, only as a function of at least one item of information about the command, without executing the command, the client embedded software comprising means of sending the response to the client external software for this purpose through the main software.
 8. Radiocommunication module as claimed in any of claims 1 to 7, characterised in that in order to enable the client embedded software to act as client supervision software: the main software comprises means of preparsing responses as a function of a determined response preparsing policy, so as to transmit responses resulting from the execution of some driver commands by execution means included in the main software, to the client embedded software and/or to the client external software; the client embedded software comprises means of processing responses switched to it by the said response preparsing means.
 9. Radiocommunication module according to claim 8, characterised in that the client embedded software comprises means of selecting the response preparsing policy applied by the said response preparsing means, among a set of response preparsing policies such as the following: responses originating from execution means are transmitted only to the client external software; responses originating from execution means are transmitted only to the client embedded software; responses originating from execution means are transmitted to the client embedded software and to the client external software.
 10. Radiocommunication module as claimed in any of claims 1 to 9, characterised in that it is included within a device belonging to the following group: radiocommunication terminals; devices other than radiocommunication terminals necessitating a wireless communication feature; modems.
 11. Radiocommunication module as claimed in any of claims 1 to 10, characterised in that the said main software comprises at least one main application associated with a set of execution functions, each enabling the execution of at least one of the said driver commands, in that each of the said client main and secondary applications is associated with a set of source functions, each enabling sending or receiving driver commands or responses to driver commands, to or from the main application, and in that the main software and/or the said client embedded software comprise an application interface used to interface the said source functions with the said execution functions.
 12. Radiocommunication module according to claim 11, characterised in that the set of source functions associated with the client main application in particular comprises a client main application initialisation source function (“wm_apmAppliInit”) that is called when the radiocommunication module is started.
 13. Radiocommunication module according to claim 12, characterised in that the set of source functions associated with the client main application comprises a source function for subscription to a service for sending messages originating from the main software (“wm_osMsgParserSubscribe”), and in that at the time of this subscription, the client main application sends the address of a message processing source function (“wm_apmAppliParser”) in which the client main application would like to receive messages from the main software, to the main software.
 14. Radiocommunication module as claimed in any of claims 11 to 13, characterised in that the set of source functions associated with the client secondary application comprises in particular a source function for initialisation of the client secondary application (“wm_app2Pipe(Init)”) that is called by the client main application.
 15. Radiocommunication module according to claim 14, characterised in that the set of source functions associated with the client secondary application comprises a source function for subscription to a service for sending messages originating from the main software (“wm_osMsgParserSubscribe”), and in that at the time of this subscription, the client secondary application sends the address of a source message processing function (“wm_app2MsgParser”) to the main software, in which the client secondary application would like to receive messages originating from the main software.
 16. Radiocommunication module as claimed in any of claims 14 and 15, characterised in that the said source initialisation function of the client secondary application comprises at least one parameter enabling the use of a dialogue mechanism between the client main application and the client secondary application.
 17. Radiocommunication module as claimed in any of claims 14 to 16, characterised in that the set of source functions associated with the client secondary application also comprises a source function for stopping the client secondary application (wm_app2Pipe(Stop)”), that is called by the client main application.
 18. Radiocommunication module as claimed in any of claims 14 to 17, characterised in that the set of source functions associated with the client secondary application comprises a source function for unsubscription from the said service for sending messages originating from the main software (“wm_osMsgParserUnsubscribe”).
 19. Radiocommunication module as claimed in any of claims 13 to 18, characterised in that the said message is a parameter of the said source function processing a message from the main software (“wm_apmAppliParser”, “wm_app2MsgParser”), and in that the structure of the said message forming the parameter comprises: a first field containing information related to the type of the said message; a second field containing the specific body of the said message.
 20. Radiocommunication module according to claim 19, characterised in that the said message type belongs to the group comprising: message containing a response to a driver command previously sent to the main software by the client embedded software; message containing an unsolicited driver command; message containing a driver command sent by a client external software through the main software; message containing a response resulting from execution of a driver command sent by the client external software, by the main software; message sent on expiration of a timeout.
 21. Radiocommunication module as claimed in any of claims 11 to 20, characterised in that the sets of source functions associated with the client main application and the client secondary application also comprise at least a source function belonging to the following group: a (“wm_atSendCommand”) function for sending at least one driver command to the main software, a first parameter of the said sending function being the said at least one driver command, a second parameter of the said sending function indicating the application(s) to which the response resulting from execution of the said driver command is sent, namely the client main application and/or the client secondary application in the client embedded software, and/or a client external application included in the client external software; a (“wm_AtUnsolicitedSubscription”) registration function with the main software to a service for reception of unsolicited driver commands, one parameter of the said registration function indicating the application(s) to which each of the unsolicited driver commands is to be redirected, namely the client main application and/or the client secondary application included in the client embedded software, and/or a client external application included in the client external software; a (“wm_atCmdPreParserSubscribe”) registration function with the main software to a driver command preparsing service, in which a parameter of the said registration function indicates the destination application(s) namely the client main application and/or the client secondary application included in the client embedded software and/or the main software to which each driver command originating from the client external software must be directed; a (“wm_atRspPreParserSubscribe”) registration function with the main software to a response preparsing service, in which a parameter of the said registration function indicates the destination application(s) namely the client main application and/or the client secondary application included in the client embedded software and/or a client external application included in the client external software to which each response resulting from the execution of a driver command by the main software must be directed; a (“wm_atSendRspExternalApp”) function for sending at least one response to the client external software, through the main software, a parameter of the said sending function being the said at least one response.
 22. Radiocommunication module as claimed in any of claims 1 to 21, characterised in that the client embedded software and the main software each use a distinct part of a RAM, and an attempt by one of the two software programs to access part of the RAM reserved for the other software will stop operation.
 23. Radiocommunication module as claimed in any of claims 1 to 22, characterised in that the said set of driver commands is a set of standard AT commands.
 24. Radiocommunication module according to claim 23, characterised in that the said set of driver commands comprises an additional AT command for loading a client software (AT+WDWL), enabling the external client software to load a new client software or a new part of the client software into the radiocommunication module, in addition to standard AT commands.
 25. Radiocommunication module as claimed in any of claims 23 and 24, characterised in that the said set of driver commands comprises an additional AT command called the deactivate command (AT+WOPEN) enabling the client external software to deactivate the client embedded software or part of the client embedded software, in addition to standard AT commands.
 26. Process for implementing a client software for driving a radiocommunication module, the said radiocommunication module being of the type hosting and executing a main software that in particular performs radiocommunication functions, the said main software comprising means of executing driver commands sent to the main software by the said client driver software and belonging to a predetermined set of driver commands, characterised in that the said Radiocommunication module also hosts and executes at least one client software, called the client embedded software, comprising a client main application and at least one client secondary application, slave of the client main application, the processing done by the said client embedded software being distributed between the said client main application and the said at least one client secondary application, and in that the client embedded software and the main software comprise means of enabling the client embedded software to perform at least one of the following two roles: the role of the said client driver software sending driver commands to the main software, and receiving responses from the main software resulting from the execution of some of the driver commands; the role of a client supervision software, managing execution of driver commands sent by the said client driver software, the said client driver software called the client external software being hosted on and executed by terminal equipment cooperating with the radiocommunication module. 